[Feat] 팀명 수정 API 추가#60
Conversation
OWNER/ADMIN이 팀명을 변경할 수 있는 PATCH /api/v1/teams/{teamId}를 추가한다.
MEMBER가 시도하면 새로 추가한 TEAM_SETTINGS_FORBIDDEN(TEAM_403_004)으로 거부한다
(TEAM_MANAGEMENT_FORBIDDEN은 "팀원 관리" 권한 문구라 팀 설정 변경에는 의미가 맞지 않아
별도 코드로 분리했다).
changeRole/removeMember/leaveTeam과 동일한 패턴을 따른다 - lockTeam으로 비관적 락을
잡고, requireActiveMember/requireActiveTeam으로 소속·활성 상태를 검증한 뒤 역할을 확인한다.
Team 엔티티의 기존 rename() 메서드(호출부 없이 방치돼 있던)를 그대로 사용했다.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
|
Warning Review limit reached
Next review available in: 25 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (7)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
1 participant
Summary
PATCH /api/v1/teams/{teamId}추가 — 팀명을 수정한다.OWNER/ADMIN만 가능,MEMBER는 새로 추가한TEAM_SETTINGS_FORBIDDEN(TEAM_403_004)으로 403.TEAM_MANAGEMENT_FORBIDDEN("팀원을 관리할 권한이 없습니다")은 팀원 관리 전용 문구라 팀 설정 변경(CAMPAIGN_MANAGEMENT_FORBIDDEN과 같은 패턴)에는 맞지 않아 별도 코드로 분리했다.Team.rename()은 이미 존재했지만 호출부가 없던 메서드다 — 이번에 처음 연결했다.changeRole/removeMember/leaveTeam과 동일한 패턴:lockTeam(비관적 락) →requireActiveMember→requireActiveTeam→ 역할 검사.TeamControllerDocs) 및 클래스 레벨 설명 갱신.Test plan
TeamMemberManagementServiceTest에renameTeam_allowsOwnerAndAdminButRejectsMember추가 (OWNER/ADMIN 성공, MEMBER 403 확인) 및mutationsRejectInactiveTeam에 rename 케이스 추가 (팀이ACTIVE가 아니면 403)🤖 Generated with Claude Code